home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d27
/
discus3x.arc
/
AS4IDU.THD
< prev
next >
Wrap
Text File
|
1991-12-04
|
11KB
|
147 lines
AS4IDU.THD
Offline IDDU for the AS/400? Field Reference files
Sparked by a question about entering a data dictionary into the AS/400 by first
typing it in offline on PCs, this discussion centers on the utility of Field
Reference Files.
.
.This is an ASCII file. READ or DOWNLOAD with any supported protocol.
Upl: Anne E. Pruitt 72335,777
IBM AS/400 FIELD REFERENCE FILES IDDU OFFLINE CONNECT DDS PC
#: 32274 S5/Technical-Big Sys
07-Jun-90 17:58:45
Sb: #AS/400 offline IDDU entr
Fm: Mark Bayern 71540,2651
To: ALL
A client of mine is converting from a Sys36 to an AS/400. They have a need to
enter the data dictionary of a purchased accounting system into the 400. The
data dictionary is currently available in printed form (approx 100 8.5x11"
pages). Their current plan is to key it in using the IDDU utility. I'd like
to offer them an option of allowing us (my company) to key it in offline (on
PC's) and then just transfer the data to the 400. From their viewpoint this
would free up terminals and personell, and from my point it should generate
some $'s, and show them that they can call on us for work in the office along
with the work we do for them on the plant floor. Does anyone know if their is
a way to generate the dictionary other than interactively on the 400? (After
all the I in IDDU stands for INTERACTIVE Data Definition Utility). If there
is could you give me a pointer to the documentation on it?
Thanks,
Mark <and just earlier this week I said in a different thread "I don't do
DP", oh well....>
#: 32289 S5/Technical-Big Sys
07-Jun-90 19:41:03
Sb: #32274-#AS/400 offline IDDU entr
Fm: Ken Werner 76657,3373
To: Mark Bayern 71540,2651
Mark,
IDDU lacks some needed power I find in DDS. IDDS will come up to speed in the
future.
You cound enter it as DDS specs on the PC, upload it, compile it as a DDS
field reference file, and there it a command to get IDDU specs from the field
reference file.
Ken
#: 32291 S5/Technical-Big Sys
07-Jun-90 19:50:05
Sb: #32289-AS/400 offline IDDU entr
Fm: will cardwell 71560,1006
To: Ken Werner 76657,3373
What do you think of field reference files? I tried using one for a user
converting from a S/36 but decided that it wasn't very helpful. When you have
to describe all of the fields in your DB in a single file, it takes a long
time to compile. There is also the problem of needing unique field names for
each file. Since RPG doesn't provide a method of qualifying field names, this
causes a big problem. It sounds like a good idea at first but then turns into
a major headache.
Will
#: 32461 S5/Technical-Big Sys
08-Jun-90 19:29:57
Sb: #32289-#AS/400 offline IDDU entr
Fm: Mark Bayern 71540,2651
To: Ken Werner 76657,3373
Ken,
Thanks for the info, I'll check into DDS when I get back the the site.
Mark
#: 32465 S5/Technical-Big Sys
08-Jun-90 20:04:01
Sb: #32291-AS/400 offline IDDU entr
Fm: Ken Werner 76657,3373
To: will cardwell 71560,1006
I strongly believe in a field reference file.
I would find a field reference file of great use in a conversion. I can
inventory that EMPNO, EMP#, PSNL#, and ID# are one and the same field.
Unless a date has a special use, I only put date in the field reference once
with the edit word desired. I reference currently used date to the field
reference date when used in a file.
#: 32490 S5/Technical-Big Sys
08-Jun-90 23:55:44
Sb: #32291-AS/400 offline IDDU entr
Fm: Patrick Townsend 73040,2224
To: will cardwell 71560,1006
Hi Will,
I would strongly recommend using a Field Reference file. It is the only thing
faintly resembling a data dictionary on the AS/400. To solve the problem of
needing different names for fields in files (I assume you r using RPG), you
can use the REFFLD keyword in DDS to refer to the field definition in the
field reference file. This will work in any type of file you might create:
database, display, printer, communications, etc. All of the IBM cross
reference utilities keep track of field and reference field definitions.
Until IBM comes out with something better (Repository Manager, AD/CYCLE ??)
you should consider using Field Reference files. This will help you make the
transition to these future products.
Patrick
#: 32498 S5/Technical-Big Sys
09-Jun-90 02:47:57
Sb: #32461-AS/400 offline IDDU entr
Fm: Tony Toews 71760,3552
To: Mark Bayern 71540,2651
Gentlemen
Re the field reference file. I found that shifting into upper and lower case
for the TEXT('lkfdl') and COLHDG('asdf') was a real PITA. So I created a file
containing all of the DDS spec's such as field name, edit code, edit word,
field size, Packed,Zoned,etc, text and colhdg. This file was indexed by field
name. The data entry program validated some of this data and by following
IBM's SAA standards I even had a 'position to' to look at twenty field names
at once. I then created the massive source file from my field name database
file and compiled it.
I, or rather my staff at my former job, created this in about two days and,
being that we were rewriting applications natively on the AS/400 as all of
their applications were S/34 & S/36 code, in less than a week this paid for
itself.
Given that you already have this reference file in place you might want to
write a program to convert from DDS source to this file.
Tony